R04. Profile import behavior

Import Profile

You can standardize the profile and apply it to multiple projects, but you can extend the profile for individual projects. The profile import feature allows you to apply standard profile revisions at any time, even if you are extending the profile in individual projects.

Import behavior

The behavior when the profile P2 is imported into the profile P1 of the project being edited is explained.

Profile Import Behavior

  • The profile is updated to be the logical sum of the profiles P1 and P2.

    Modify operation Behavior
    Add with P2 Add as is
    Deleted on P2 Keep contents on P1
    Changed with P2 (with differences) Overwritten with the contents of P2
    No change in P2 (no difference) No change

  • The data in the profile is judged not by name but by internal management ID, and if they are the same, it is judged by the difference in contents whether there is any change.

  • Not only the entity and view definition defined in the metamodel, but also the individual fields held by the entity are judged to have the same identity by the internally managed ID.
  • The data moved between packages in the metamodel is also judged to have the same identity by the ID of the internal management, and is moved according to the P2 package structure.
  • If the name of additional data is duplicated, the name of P1 is automatically corrected and the name of P2 is maintained.
  • The order in the metamodel follows the order in P2. The data of P1 deleted by P2 goes after the data of P2.